Summary

• add a server reconciliation regression test for the case where persisted managed runtime metadata no longer matches the desired binary/launch configuration on boot
• verify that boot reconciliation terminates the old process, deletes instance.json, and does not implicitly respawn the instance when auto_start=false
• strengthen coverage around the same boot-path family that previously showed fragile behavior during local smoke validation
• keep the change test-only and scoped to one high-risk backend behavior

Validation

• zig build test -Dembed-ui=false -Dbuild-ui=false --summary all
• npm --prefix ui ci --no-audit --no-fund
• npm --prefix ui run build
• bash tests/test_e2e.sh
• zig fmt --check src/
• git diff --check

Notes

• this PR does not change production code; the new regression test passes against current main
• the coverage target is intentionally narrow so the boot-reconciliation contract is locked down before broader supervisor/integration work lands
• a natural next Phase 5 follow-up is either installer rollback coverage or orchestration proxy error-mapping coverage